home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
500 MB Nyheder Direkte fra Internet 2
/
500 MB nyheder direkte fra internet CD 2.iso
/
start
/
data
/
text
/
faq-0594.txt
< prev
next >
Wrap
Text File
|
1995-05-08
|
43KB
|
946 lines
Archive-name: games/mud-faq/part2
FREQUENTLY ASKED QUESTIONS: MUD CLIENTS AND SERVERS
This is part 2 in a 3 part series of FAQs.
$Id: mudfaq-p2.html,v 1.3 1995/03/13 23:27:15 jds Exp jds $
Disclaimer:This document may be seen to be biased towards TinyMUDs.
This is because the maintainer mainly plays those types of servers,
not because she thinks they are inherently better or worse than
other types of servers. However, this document is meant to be
generalized and useful for all MUDdom, and so corrections and
contributions are always welcome.
Table of Contents
* Client Information
+ 2.1. What is a client?
+ 2.2. Where do I get clients?
+ 2.3. What operating systems do clients run on?
+ 2.4. Is there anything wrong with running a client?
+ 2.5. What different clients are available? [Client List]
* Glossary of Client terms
* Server Information
+ 2.6. What is a server?
+ 2.7. Where do I get servers?
+ 2.8. What operating systems to servers run on?
+ 2.9. Is there anything wrong with running a server?
+ 2.10. What different servers are available? [Server List]
* General Information
+ 2.11. What do I do if my client/server won't compile?
+ 2.12. Should I read the documentation of whatever client or
server I select?
+ 2.13. What is FTP, and how do I use it?
CLIENT INFORMATION
2.1. What is a client?
Clients are programs, usually written in C, that connect up to
servers. Telnet is one such client program. Many clients written for
MUDs have special added bonus features through which they filter the
output; most, for instance, separate your input line from the output
lines and wraps words after 80 columns. Some also have a macro-
writing capability which allows the user to execute several commands
with just a few keypresses. Some allow you to highlight output coming
from certain players or suppress it altogether. Still other clients
make the sometimes tedious task of building new areas a breeze.
2.2. Where do I get clients?
Listed below is a list of clients, and a site or two where they can be
ftped from. If the site is down, your best bet is to ask around. In
general, ftp.tcp.com and ftp.math.okstate.edu are good places to look.
Directions for how to ftp and unarchive clients are at the end of this
FAQ.
2.3. What operating systems do clients run on?
Most use BSD Unix, although many also run under SysV Unix. Some run
under VMS with either MultiNet or Wollongong networking, a few new
ones run on a Macintosh, and there's even one for IBM VM.
2.4. Is there anything wrong with running a client?
Not usually. Clients can be large when compiled, especially if they
have lots of nifty features. They don't take up much CPU time at all.
It is recommended that you ask your friendly systems administrator or
other machine-responsible person if it's okay for you to install one
on the system, if only for the reason that someone else might already
have done so, and you might be able to save space by sharing with
them. If there's a no games policy at your site, don't try to sneak by
it with a client -- their activities are easily detectable. Be good.
2.5. What different clients are available?
Here's a reasonably accurate listing of available clients. Please note
that I have not tested each of these, and they're not guaranteed to
work for you. If your favorite client isn't listed here, please drop a
short note describing the client's features and where it can be ftp'd
from to jds@math.okstate.edu.
The following clients are detailed below. Directions for how to ftp
and unarchive clients and servers can be found at the end of this FAQ.
Unix Clients
TinyTalk, TinyFugue, TclTT, VT, LPTalk, SayWat, PMF, TinTin,
TinTin++, TUsh, LPmudr
Emacs Clients
MUD.el, TinyTalk.el, LPmud.el, CLPmud.el, MyMud.el
VMS Clients
tfVMS, TINT, TINTw, DINK, FooTalk
WinSock Clients
WinMud, VWMud, WinWorld, MUTT, MudWin
Misc Clients
REXXTALK, MUDDweller, Mudling, MUDCaller, BSXMUD Clients
_________________________________________________________________
TinyTalk
Runs on BSD or SysV. Latest version is 1.1.7GEW. Designed
primarily for TinyMUD-style muds. Features include line
editing, command history, hiliting (whispers, pages, and
users), gag, auto-login, simple macros, logging, and
cyberportals.
ftp.math.okstate.edu:/pub/muds/clients/UnixClients
parcftp.xerox.com:/pub/MOO/clients
ftp.tcp.com:/pub/mud/Clients
TinyFugue
Runs on BSD or SysV. Latest version is 3.2beta4. Commonly known
as 'tf'. Designed primarily for TinyMUD-style muds, although
will run on LPMUDs and Dikus. Features include regexp hilites
and gags, auto-login, macros, line editing, screen mode,
triggers, cyberportals, logging, file and command uploading,
shells, and multiple connects.
ftp.math.okstate.edu:/pub/muds/clients/UnixClients/tf
ftp.tcp.com:/pub/mud/Clients
TclTT
Runs on BSD. Latest version is 0.9. Designed primarily for
TinyMUD-style muds. Features include regexp hilites, regexp
gags, logging, auto-login, partial file uploading, triggers,
and programmability.
ftp.white.toronto.edu:/pub/muds/tcltt
ftp.math.okstate.edu:/pub/muds/clients/UnixClients
VT
Runs on BSD or SysV. Latest version is 2.15. Must have vt102
capabilities. Useable for all types of muds. Features include a
C-like extension language (VTC) and a simple windowing system.
ftp.math.okstate.edu:/pub/muds/clients/vt
ftp.tcp.com:/pub/mud/Clients
LPTalk
Runs on BSD or SysV. Latest version is 1.2.1. Designed
primarily for LPMUDs. Features include hiliting, gags,
auto-login, simple macros, logging.
ftp.math.okstate.edu:/pub/muds/clients/UnixClients
SayWat
Runs on BSD. Latest version is 0.30beta. Designed primarily for
TinyMUD-style muds. Features include regexp hilites, regexp
gags, macros, triggers, logging, cyberportals, rudimentary
xterm support, command line history, multiple connects, and
file uploading.
ftp.math.okstate.edu:/pub/muds/clients/UnixClients
PMF
Runs on BSD. Latest version is 1.13.1. Usable for both LPMUDs
and TinyMUD-style muds. Features include line editing,
auto-login, macros, triggers, gags, logging, file uploads, an
X-window interface, and ability to do Sparc sounds.
ftp.lysator.liu.se:/pub/lpmud/clients
ftp.math.okstate.edu:/pub/muds/clients/UnixClients
TinTin
Runs on BSD. Latest version is 2.0. Designed primarily for
Dikus. Features include macros, triggers, tick-counter
features, and multiple connects.
ftp.math.okstate.edu:/pub/muds/clients/UnixClients
TinTin++
Runs on BSD or SysV. Latest version is 1.5pl5. Derived and
improved from TinTin. Additional features include variables,
faster triggers, and a split screen mode.
ftp.princeton.edu:/pub/tintin++/dist
ftp.math.okstate.edu:/pub/muds/clients/UnixClients
TUsh
Runs on BSD or SysV. Latest version is 1.74. Features include
hiliting, triggers, aliasing, history buffer, and screen mode.
ftp.math.okstate.edu:/pub/muds/clients/UnixClients
LPmudr
Runs on BSD or SysV. Latest version is 2.7. Designed primarily
for LPMUDs. Features include line editing, command history,
auto-login and logging.
ftp.math.okstate.edu:/pub/muds/clients/UnixClients
MUD.el
Runs on GNU Emacs. Usable for TinyMUD-style muds, LPMUDs, and
MOOs. Features include auto-login, macros, logging,
cyberportals, screen mode, and it is programmable.
parcftp.xerox.com:/pub/MOO/clients
ftp.math.okstate.edu:/pub/muds/clients/UnixClients
TinyTalk.el
Runs on GNU Emacs. Latest version is 0.5. Designed primarily
for TinyMUD-style muds. Features include auto-login, macros,
logging, screen mode, and it is programmable.
ftp.tcp.com(128.95.10.106):/pub/mud/Clients
ftp.math.okstate.edu:/pub/muds/clients/UnixClients
LPmud.el
Runs on GNU Emacs. Designed primarily for LPMUDs. Features
include macros, triggers, file uploading, logging, screen mode,
and it is programmable.
ftp.lysator.liu.se:/pub/lpmud/clients
ftp.math.okstate.edu:/pub/muds/clients/UnixClients
CLPmud.el
Runs on GNU Emacs. Designed primarily for LPMUDs. Similar to
LPmud.el, but with the added capability for remote file
retrieval, editing in emacs, and saving, for LPMud wizards.
mizar.docs.uu.se:/pub/lpmud
MyMud.el
Runs on GNU Emacs. Latest version is 1.31. Designed primarily
for LPMUDs and Dikus. Features include screen mode, auto-login,
macros, triggers, autonavigator, and it is programmable.
ftp.math.okstate.edu:/pub/muds/clients/UnixClients
ftp.tcp.com:/pub/mud/Clients
tfVMS
VMS version of TinyFugue (see above). Uses Wollongong
networking. Latest version is 1.0b2.
ftp.math.okstate.edu:/pub/muds/clients/VMSClients
TINT
Runs on VMS with MultiNet networking. Latest version is 2.2.
Designed primarily for TinyMUD-style muds. Features include
hiliting (whispers, pages, users), gags, file uploading, simple
macros, screen mode. See also TINTw.
ftp.math.okstate.edu:/pub/muds/clients/VMSClients
TINTw
Runs on VMS with Wollongong networking. See TINT.
ftp.math.okstate.edu:/pub/muds/clients/VMSClients
ftp.tcp.com:/pub/mud/Clients
DINK
Runs on VMS with either Wollongong or MultiNet networking.
Similar to TINT. No longer supported by the author.
ftp.math.okstate.edu:/pub/muds/clients/VMSClients
ftp.tcp.com:/pub/mud/Clients
FooTalk
Runs on VMS with MultiNet networking and BSD Unix. Primarily
designed for TinyMUD-style muds. Features include screen mode,
and it is programmable. See RispTalk below.
ftp.math.okstate.edu:/pub/muds/clients/VMSClients
ftp.math.okstate.edu:/pub/muds/clients/UnixClients
WinMud
Runs on MS Windows using WinSock. Primarily designed for LPs
and DikuMUDs. Features include simple macros.
ftp.cybernetics.net:/pub/users/lymang
VWMud
Runs on MS Windows using WinSock. Features include macros and
triggers.
ftp.primenet.com:/pub/users/kslewin
WinWorld
Runs on MS Windows using WinSock.
ftp.mgl.ca:/pub/winworld
MUTT
Runs on MS Windows using WinSock. Latest version is 01i. Name
stands for Multi-User Trivial Terminal. Features include
scripting, multiple connects, triggers, macros, logging, etc.
caisr2.cwru.edu:/pub/mud
ftp.graphcomp.com:/pub/msw/mutt
MudWin
Runs on MS Windows using WinSock. Features include command
history, simple macros, and logging.
ftp.microserve.com:/pub/msdos/winsock
REXXTALK
Runs on IBM VM. Latest version is 2.1. Designed primarily for
TinyMUD-style muds. Features include screen mode, logging,
macros, triggers, hilites, gags, and auto-login. Allows some
IBM VM programs to be run while connected to a foreign host,
such as TELL and MAIL.
ftp.math.okstate.edu:/pub/muds/clients/misc
MUDDweller
Runs on any Macintosh. Latest version is 1.2. Connects to a MUD
through either the communications toolbox or by MacTCP. Usable
for both LPMUDs and TinyMUD-style muds. Current features
include multiple connections, a command history and a built-in
MTP client for LPMUDs.
rudolf.ethz.ch:/pub/mud
mac.archive.umich.edu:/mac/util/comm
ftp.tcp.com:/pub/mud/Clients
Mudling
Runs on any Macintosh. Latest version is 0.9b26. Features
include multiple connections, triggers, macros, command line
history, separate input and output windows, and a rudimentary
mapping system.
imv.aau.dk:/pub/Mudling
ftp.math.okstate.edu:/pub/muds/clients/misc
MUDCaller
Runs under MSDOS. Latest version is 2.50. Requires an Ethernet
card, and uses the Crynwr Packet drivers. Does NOT work with a
modem. (If you telnet in MSDOS, you can probably use this.)
Features include multiple connections, triggers, command-line
history, scrollback, logging, macros, and separate input and
output windows.
ftp.tcp.com:/pub/mud/Clients
ftp.math.okstate.edu:/pub/muds/clients/misc
oak.oakland.edu:/pub/msdos/pktdrvr
BSXMUD Clients
These clients run on various platforms, and allow the user to
be able to see the graphics produced by BSXMUDs. BSXMUDs are
generally LPMUDs (but not necessarily) who have been hacked to
enable the sending of polygon graphics coordinates to
BSXclients, thus letting you play a graphic MUD instead of just
a text-based one.
For Amiga: modem or TCP/IP - AmigaBSXClient2_2.lha
For PC: requires a modem - msclient.lzh AND x00v124.zip
For X11: sources, version 3.2 - bsxclient3_8c.tar.Z
For Sun4: binary - client.sparc.tar.Z
Also available are programs to custom-draw your own graphics
for a BSXMUD: - muddraw.tar.gz, bsxdraw.zoo
ftp.lysator.liu.se:pub/lpmud/bsx
ftp.math.okstate.edu:/pub/muds/BSXstuff
_________________________________________________________________
GLOSSARY OF CLIENT TERMS
Auto-login
Automatically logs into the game for you.
Hiliting
Allows boldface or other emphasis to be applied to some text.
Often allowed on particular types of output (e.g. whispers), or
particular players. "Regexp" means that UNIX-style regular
expressions can be used to select text to hilite.
Gag
Allows some text to be suppressed. The choice of what to
suppress is often similar to hiliting (players or regular
expressions).
Macros
Allows new commands to be defined. How complex a macro can be
varies greatly between clients; check the documentation for
details.
Logging
Allows output from the MUD to be recorded in a file.
Cyberportals
Supports special MUD features which can automatically reconnect
you to another MUD server.
Screen Mode
Supports some sort of screen mode (beyond just scrolling your
output off the top of the screen) on some terminals. The exact
support varies.
Triggers
Supports events which happen when certain actions on the MUD
occur (e.g. waving when a player enters the room). (This can
nearly always be trivially done on programmable clients, even
if it isn't built in.)
Programmable
Supports some sort of client-local programming. Read the
documentation.
Some of these clients are more featured than others, and some require
a fair degree of computer literacy. TinyTalk and TinyFugue are among
the easiest to learn; Tcltt and VT are more professional. Caveat
Emptor. Since many MUDders write their own clients, this list can
never be complete. As above, ask around.
_________________________________________________________________
SERVER INFORMATION
2.6. What is a server?
A server is a program which accepts connections, receives data, mulls
it over, and sends out some output. In the MUD world, the server keeps
track of the database, the current players, the rules, and sometimes
the time (or the heartbeat). Servers are usually very large C programs
which maintain a small-to-enormous database of the objects, rooms,
players and miscellany of the MUD.
2.7. Where do I get servers?
Below (see question 2.10)there is a list of different types of
servers, complete with ftp sites on which they can be found. Be aware
that this list is far from complete, as new servers pop up constantly,
and the existing ones are still being developed.
2.8. What operating systems to servers run on?
Most servers require some form of UNIX, be it BSD or SysV. A few
servers are being ported to VMS nowadays, and there are a few which
have versions for MS-DOS and Amigas.
2.9. Is there anything wrong with running a server?
Because of their size and their constant computational activities,
servers can be extremely CPU-intensive and can even be crippling to
any other work done on that computer. Even if they're not
CPU-intensive, most MUDs can take up a fair amount of disk space -
anywhere from 10 to 90 megs, which could impact the other users on the
machine. Do not ever run a MUD server on a machine illicitly or
without express permission from the person responsible for the
machine. Many universities and companies have strict policies about
that sort of behavior which you don't want to cross.
Of course, people who don't know any better start up illicit MUDs all
the time. Apart from the possibility of losing all your work and
energy to one press of a sysadmin's finger, there's no harm done to
the player. But we must stress: running a MUD where you shouldn't can
get you into a whole new world of hurt. Don't take the chance, it's
not worth it.
2.10. What different servers are available?
There are probably as many MUD server types as there are MUDs. Since
everyone has their own opinions as to what MUDs should be like, and
since the server source can be edited, most MUDs have site-specific
fixtures in them. However, there are a few main protoMUDs (also called
'vanilla versions' because they haven't been 'flavored' yet). Note
that this list is not complete, and that it may contain errors in fact
or judgement, but is deemed pretty much right as of this writing.
Corrections/additions to jds@math.okstate.edu are welcomed.
There are essentially three groups of muds:
* Combat-oriented MUDs (LP/Diku/etc)
* TinyMUD and its direct descendants, aka social-oriented MUDs
* Miscellaneous
The majority of the muds in the miscellaneous category are not
combat-oriented muds at all, and indeed many take after TinyMUD in
most things. However, as these muds are not a direct derivative of the
original TinyMUD code, I've stuck them in their own category. The
authors listed for each server are very probably not the people
currently working on that code. To find out who's currently in charge
of the code, either ftp the latest version and look for a README file,
or ask around.
A note on the term combat-oriented: this generally means that combat
is an inherent part of the culture of the mud. A flight-simulator
could be called a combat-oriented game, just as truely as your typical
shoot-em-up game could be. A social-oriented mud has a different
focus, one dependent either on roleplaying social interactions (which
MAY include combat!), or on not roleplaying at all, but merely talking
with friends or other such benign things. It should be emphasized that
simply because a given server is listed in the combat-oriented area,
it does not necessarily follow that it must be a combat-oriented MUD.
Most servers are fairly flexible, and can be used for social and
combat uses alike, as well as for business and education.
Detailed listings of the following servers are below. Directions for
how to ftp and unarchive servers can be found at the end of this FAQ.
Combat-Oriented MUDs
MUD, AberMUD, LPMUD, DGD, DikuMUD, YAMA, UriMUD, Ogham,
CircleMUD, AmigaMUD
Social-Oriented MUDs
TinyMUD, TinyMUCK v1.*, TinyMUSH, TinyMUCK v2.*, TinyMUSE,
TinyMAGE, MUG, TeenyMUD
Misc MUDs
UberMUD, MOO, LambdaMOO, SMUG, UnterMUD
_________________________________________________________________
Combat-Oriented MUDs
MUD
The original, by Richard Bartle and Roy Trubshaw, written back
in 1978. An advanced version of MUD2 is now running on
CompuServe under the name of "British Legends". A few MUD2s can
still be found running here and there. The three known ones are
portal.aladdin.co.uk, craic.iol.ie, and Iplay Online at
199.182.210.2. Source generally not available.
AberMUD
One of the first adventure-based MUDs. Players cannot build. In
later versions, a class system was added, and wizards can build
onto the database. It's named after the university at which it
was written, Aberystwyth. Latest version is 5.21.5. Supports
all the usual in combat game design, including BSX graphics and
MudWHO. Not too big, and it will run under BSD and SYSV. Amiga
TCP/IP support now included.
Author, contact address, and mailing list address is
A.Cox@swan.ac.uk.
sunacm.swan.ac.uk:/pub/misc/AberMUD5/SOURCE
LPMUD
The most popular combat-oriented MUD. Players cannot build. Be
warned, though: LPMUD servers version 3.* themselves are very
generic - all of the universe rules and so forth are written in
a separate module, called the mudlib. Most LPMUDs running are
written to be some sort of combat system, which is why I've
classified them here, but they don't have to be! Wizards can
build onto the database, by means of an object-oriented C-like
internal language called LP-C. It's named after its primary
author, Lars Pensj|. Latest version is 3.2, aka Amylaar. Fairly
stable, and size varies from medium to large. Driver (server)
versions seem to have split into several main variants, not
counting possible mudlibs (databases) available. Amylaar, CD,
and MudOS are the current favorites. For further information,
email to amylaar@meolyon.hanse.de.
There is a port of 3.1.2 for Amigas, called amud, now included
in LPMUD v3.2. For further information email to
mateese@ibr.cs.tu-bs.de.
See the rec.games.mud.lp FAQ for more info.
ftp.lysator.liu.se:/pub/lpmud
ftp.cd.chalmers.se:/pub/lpmud/cdlib
ftp.tu-bs.de:/pub/games/lpmud
ftp.ccs.neu.edu:/pub/mud/drivers/mudos
There is a port of 3.1.2 for MSDOS, that requires at least a
'386 to run. It accepts connections from serial ports.
ftp.ccs.neu.edu:/pub/mud/drivers/lpmud/msdos
DGD
Written by Felix Croes. A reimplementation from scratch of the
LPMUD server. It is disk-based, and thus uses less memory. It's
also smaller and lacks many of the features of the other LPMUD
servers, though it is capable of simulating most of those
features in LPC. Many DGDs are simulating an LP, but there are
several MUDs that now use DGD to simulate a MOO variant. The
name stands for Dworkin's Generic Driver. Stable. Has been
ported to Atari ST and Commodore Amiga.
ftp.lysator.liu.se:/pub/lpmud/drivers/dgd
DikuMUD
Newer than LPMud, and gaining in popularity. Almost identical
from the players' point of view. Uses a guild system instead of
a straight class system. Wizards can add on to the database,
but there is no programming language, as in LP. It's named
after the university at which it was written, Datalogisk
Institut Koebenhavns Universitet (Dept. of Datalogy, University
of Copenhagen).
coyote.cs.wmich.edu:/pub/Games/DikuMUD
YAMA
PC mud writing system, using waterloo wattcp. Runs on a 640K
PC/XT or better. Runs best with about a 1Mb ram disk, but is
fine without. A separate windows version (yamaw) runs under
windows and allows you to run a mud on a 286 or higher without
taking over the machine.
sunacm.swan.ac.uk:/pub/misc/YAMA
UriMUD
Developed from an LPMud2.4.5, the code structure is very
similar. Features include better speed, flexibility, stronger
LPC, and the ability to handle multiple mudlibs under one
parser. Latest version is 2.5.
urimud.isp.net:/urimud/src
Ogham
From the players' point of view, similar to LPMUD. No
programming language or database, as mud compiles to a single
binary executable. Latest version is 1.5.
ftp.ccs.neu.edu:/pub/mud/servers/ogham
ftp.math.okstate.edu:/pub/muds/servers
CircleMUD
Derivative of DikuMUD Gamma v0.0. Developed by Jeremy Elson
(jelson@cs.jhu.edu). Less buggy and tighter code all in all.
Latest version is 2.20. Also see URL
http://www.cs.jhu.edu/other/jelson/circle.html
ftp.cs.jhu.edu:/pub/CircleMUD
sunsite.unc.edu:/pub/Linux/games/muds
ftp.math.okstate.edu:/pub/muds/servers
AmigaMUD
Written by scratch for Commodore Amiga computers. Includes
custom client which supports graphics and sound. Disk based,
fast programming language, standard scenario including built-in
mail and bboards. Obtained from the Aminet ftp sites.
ftp.wustl.edu:/pub/aminet/game/role/AMClnt.lha, AMSrv.lha
_________________________________________________________________
TinyMUD-style MUDs
TinyMUD
The first, and archetypical, socially-oriented MUD. It was
inspired by and looks like the old VMS game Monster, by Rich
Skrenta. Players can explore and build, with the basic @dig,
@create, @open, @link, @unlink, @lock commands. Players cannot
teleport, and couldn't use @chown or set things DARK until
later versions. Recycling didn't exist till the later versions,
either. It's called 'Tiny' because it is - compared to the
combat-oriented MUDs. Original code written by Jim Aspnes. Last
known version is 1.5.5. Not terribly big, and quite stable.
ftp.math.okstate.edu:/pub/muds/servers
primerd.prime.com:/pub/games/mud/tinymud
There is a PC port of TinyMUD, along with some extra code. It
accepts connections from serial ports.
ftp.tcp.com:/pub/mud/TinyMUD
There is a modified version of TinyMUD called PRISM, that works
for PCs, Atari STs, and most Unixes. It also comes with a
internal BSX client for MSDOS.
lister.cc.ic.ac.uk:/pub/prism
TinyMUCK v1.*
The first derivative from TinyMUD. Identical to TinyMUD, except
that it added the concept of moveable exits, called @actions.
Also introduced the JUMP_OK flag, which allows players to use
@teleport, and @recycle, which TinyMUD later added. Its name,
MUCK, is derived from MUD, and means nothing in particular.
Original code written by Stephen White. Latest stable verion is
1.2.c&r, which brought TinyMUCKv1 up to date with later TinyMUD
things. Not terribly big.
ftp.math.okstate.edu:/pub/muds/servers
TinyMUSH
The second derivative from TinyMUD. Also identical to TinyMUD,
with the addition of a very primitive script-like language.
Introduced JUMP_OK like TinyMUCK, and has recycling, except it
is called @destroy. Also introduced the concept of PUPPETs, and
other objects that can listen. In later versions the script
language was extended greatly, adding math functions and many
database functions. In the latest version, 2.0.*, it's gone to
a disk-basing system as well. Its name, MUSH, stands for
Multi-User Shared Hallucination. Original code written by Larry
Foard. The latest non- disk-based version is PennMUSH1.50p10g5,
which is quite similar to 2.0 from the user's point of view.
Both the disk-based version and the non-disk-based version are
being developed at the same time (PennMUSH is now being
developed under the name PennMUSH-Dune). TinyMUSH is more
efficient in some ways than TinyMUD, but winds up being larger
because of programmed objects. Version 2.0 in general uses less
memory but a great deal more disk space. 2.0 may also be able
to be run under VMS, as well as both BSD and SysV UNIX. Most
recent version is 2.0.10p6.
caisr2.caisr.cwru.edu:/pub/mush
mellers1.psych.berkeley.edu:/pub/DuneMUSH/Source
ftp.cis.upenn.edu:/pub/lwl
primerd.prime.com:/pub/games/mud/tinymush
ftp.tcp.com:/pub/mud/TinyMUSH
TinyMUCK v2.*
TinyMUCKv1.* with a programming language added. The language,
MUF (multiple user forth), is only accessible to people with
the MUCKER flag. Changed the rules of the JUMP_OK flag
somewhat, to where it's nice and confusing now. MUF is very
powerful, and can do just about anything a wizard can. Original
version 2.* code written by Lachesis. Latest version is 2.3b,
with several varieties (FBMUCK and DaemonMUCK 0.14 the most
common). The name doesn't mean anything. Can be quite large,
especially with many programs. Mostly stable.
ftp.tcp.com:/pub/mud/TinyMUCK
TinyMUSE
A derivative of TinyMUSH. Many more script-language extensions
and flags. Reintroduced a class system, a-la combat-oriented
MUDs. The name stands for Multi-User Simulation Environment.
Latest version is 1.7b4. Not very stable.
mcmuse.mc.maricopa.edu:/muse/server
caisr2.caisr.cwru.edu:/pub/mush/muse
TinyMAGE
The bastard son of TinyMUSH and TinyMUCK. It combines some of
MUSH's concepts (such as puppets, @adesc/@asucc, several
programming functions, and a few flags) with TinyMUCK2.x.
Interesting idea, really busted code. The name doesn't mean
anything. Latest version is 1.1.2.
ftp.tcp.com:/pub/mud/TinyMAGE
MUG
Derivative of TinyMUD 1.4.1. It's name stands for Multi-User
Game. Powerful but awkward programming language, which is an
extension of the user language; primitive notion of Puppets;
inheritance; sane variable/property matching; arrays and
dictionaries in hardcode. Somewhat non-standard and buggy in a
few places.
Requires gcc.2.4.5 or greater (or other good C++ compiler) to
compile. Available by e-mail from wizard@cs.man.ac.uk;
development site is UglyMUG (wyrm.cs.man.ac.uk 6239).
TeenyMUD
A TinyMUD clone, written from scratch. Its main feature is that
it is disk based. Original code written by Andrew Molitor.
Latest version is 1.3. Very small, and mostly stable.
fido.econ.arizona.edu:/pub/teeny
_________________________________________________________________
Miscellaneous
UberMUD
The first MUD where the universe rules are written totally in
the internal programming language, U. The language is very
C/pascal-like. The permissions system is tricky, and writing up
every universe rule (commands and all) without having big
security holes is a pain. But it's one of the most flexible
muds in existance. Great for writing up neat toys. It's also
disk-based. Original code written by Marcus J Ranum. Latest
version is 1.13. Small in memory, but can eat up disk space.
Quite stable.
decuac.dec.com:/pub/mud
ftp.white.toronto.edu:/pub/muds/uber
ftp.math.okstate.edu:/pub/muds/servers
MOO
An Object-Oriented MUD. Unfortunately, the first few versions
weren't fully object oriented. Later versions fixed that
problem. There is a C-like internal programming language, and
it can be a bit tricky. Original code written by Stephen White.
Last version is 2.0a.
NO KNOWN SITE
LambdaMOO
An offshoot of MOO. Added more functionality, many new
features, and a great deal more stability, in a general rewrite
of the code. This is the only version of MOO that is still
being developed, by Pavel Curtis. Latest version is 1.7.8p3.
parcftp.xerox.com:/pub/MOO
SMUG
Also known as TinyMUD v2.0. It has an internal programming
language, and it does have some inheritance. Surprisingly
similar to MOO in some ways. SMUG stands for Small Multi User
Game. Original code written by Jim Aspnes.
ftp.tcp.com:/pub/mud/Smug
UnterMUD
A network-oriented MUD. It's disk-based, with a variety of db
layers to choose from. An UnterMUD can connect directly to
other UnterMUDs, and players can carry stuff with them when
they tour the Unterverse. This can be a bit baffling to a new
user, admittedly, but those people already familiar with the
old cyberportals and how they work (invented way back with the
original TinyMUD) will adjust to the new real cyberportals
easily. There is both a primitive scripting language and much
of the U language from UberMUD built in, as well as a combat
system that can be compiled in if wanted. The parsing can be a
bit odd, especially if you're used to the TinyMUD-style parser.
Unter is also the only MUD that can run under BSD Unix, SysVr4
Unix, and VMS with MultiNet networking, with little to no
hacking. Original code written by Marcus J Ranum.
Latest version is 2.1. Small in memory, but can eat up a lot of
disk space.
ftp.math.okstate.edu:/pub/muds/servers
decuac.dec.com:/pub/mud
ftp.tcp.com:pub/mud/UnterMUD
Note: just because we say something's available doesn't mean we have
it. Please don't ask us; ask around for ftp sites that might have
them, or try looking on ftp.tcp.com or ftp.math.okstate.edu.
_________________________________________________________________
GENERAL INFORMATION
2.11. What do I do if my client/server won't compile?
Your first best bet is to check out the documentation and see if
someone is listed as 'supporting' (i.e. generally responsible for) the
program. If they are, send them a short, well-written e-mail note
explaining your hardware and software completely as well as a
transcript of the error. Do not post to the internet unless all other
realistic options have been considered and taken -- generally
speaking, most readers will not be interested in your dilemma and may
get upset that you're wasting their time. Since MUDs have probably
been compiled on every single platform since the Cyber 3000, there's a
good chance that asking around the subculture will get you the answers
you crave. Do not mail me. I probably won't know.
2.12. Should I read the documentation of whatever client or server I
select?
Yes.
2.13. What is FTP, and how do I use it?
FTP stands for File Transfer Protocol, and is a way of copying files
between networked computers. The best way to learn about ftp is to get
the FTP FAQ, by emailing mail-server@rtfm.mit.edu with
send usenet/news.answers/ftp-list/faq
in the body of the message.
Not all ftps are alike, but here's a sample session:
% ftp ftp.math.okstate.edu
Connected to ftp.math.okstate.edu.
220 ftp.math.okstate.edu FTP server (SunOS 4.1) ready.
Name (ftp.math.okstate.edu:jds): ftp <-- use 'ftp' as your login
331 Guest login ok, send ident as password.
Password: <-- use your email addr as pwd
230 Guest login ok, access restrictions apply.
ftp> cd pub/muds/clients <-- how to change directories
250 CWD command successful.
ftp> dir <-- ls also works
200 PORT command successful.
150 ASCII data connection for /bin/ls (139.78.112.6,4011) (0 bytes).
total 2310
-rw-r--r-- 1 4002 4002 34340 Feb 6 1992 amigaclient.lzh
...etc etc...
-rw-r--r-- 1 4002 4002 43093 Dec 13 1991 tinytalk.117.shar.Z
226 ASCII Transfer complete.
2631 bytes received in 0.7 seconds (3.6 Kbytes/s)
ftp> bin <-- VERY IMPORTANT! binary transfers
200 Type set to I.
ftp> get tinytalk.117.shar.Z <-- get filename
200 PORT command successful.
150 ASCII data connection for tinytalk.117.shar.Z (139.78.112.6,4012) (43093
bytes).
226 ASCII Transfer complete.
local: tinytalk.117.shar.Z remote: tinytalk.117.shar.Z
43336 bytes received in 0.28 seconds (1.5e+02 Kbytes/s)
ftp> bye <-- how to quit ftp
221 Goodbye.
%
Now that you've successfully ftped a file, you must unarchive it.
There are many ways of archiving files; so many that they couldn't
possibly all be listed here. In general, though, if a file ends in:
.Z
uncompress filename
.z
gunzip filename
.gz
gunzip filename
.tar
tar -xvf filename
.shar
sh filename
.zip
unzip filename
Generally, once you've unarchived your client or server, you must
still compile it. This varies widely depending on the system you're on
and the particular client or server. Your best bet is to look for a
README or INSTALLATION file or something equally obvious, and then if
you're still unsure, ask someone locally to help you out.
_________________________________________________________________
This posting has been generated as a public service. If you have any
suggestions, questions, additions, comments or criticisms concerning
this posting, contact Jennifer Smith, aka Moira
(jds@math.okstate.edu). Other Frequently Asked Questions (FAQ)
postings contain information on MUDs, MUDding, and RWHO. While these
items aren't necessary, they are quite useful. I'd also like to
thank cthonics (felixg@coop.com) for his help in writing these FAQs,
IronThoughts and Tarrant for their help, and everyone else for
helpful comments and suggestions. Last but not least, a special
thanks goes out to Richard Bartle, for getting MUDs started in the
first place.
The most recent versions of these FAQs are archived on
ftp.math.okstate.edu in pub/muds/misc/mud-faq, plus on rtfm.mit.edu
in the news.answers archives. HTML-ized versions are available at
URL http://math.okstate.edu/~jds/mudfaqs.html. Have fun! - Moira
_________________________________________________________________
Jennifer Smith / jds@math.okstate.edu
--
Jennifer Smith
jds@math.okstate.edu
On MUDs: Moira, etc. | But still I fear and still
Here, have a clue. Take two, they're small. | I dare not Laugh at the Madman.